Laravel 5.6 has those new changes

by Devin Yang
(This article was automatically translated.)

Published - 8 years ago ( Updated - 8 years ago )

Laravel 5.6 is scheduled to be released in February 2018, what changes? Let's see.

1. In Laravel 5.6, Argon2i password hashing algorithm will be supported. (Argon2i Password Hashing Algorithm)
Argon2 is available in three versions:
1. Argon2d resists GPU cracking attacks to the greatest extent.
2. Argon2i is optimized to resist side-channel attacks.
3. Argon2id is a hybrid version, the above two versions are mixed.

It doesn't matter if you don't understand it, I don't understand it anyway, the point is, it's safe to be sure anyway.
This is in the Open Cryptography Competition (PHC), designed by Alex Biryukov, Daniel Dinu and Dmitry Khovratovich on July 20, 2015, and finally selected as the PCH winner. The goal of the Open Cryptography Competition (PHC) is Select more cryptographic hash functions that can be recognized as standard.

The old bcrypt will continue to be supported and will remain as the default. After the official release of Laravel 5.6,
If you're using a new project it's worth considering switching to Argon2i.

Second, there are new Blade Directives in Laravel 5.6.
5.5 hours


{{ csrf_field() }}
{{ method_field('PUT') }}


After 5.6, you can use the directives as follows, which is even simpler.


@method('put')
@csrf


3. Laravel 5.6 will remove the artisan optimzie command.

You may have noticed that in 5.5, after entering php artisan, you will see that the command has been listed as deprecated

Help:

Optimize the framework for better performance ( deprecated )



Since PHP 7 implements PHP op-code caching, this command is no longer needed.



As an aside, the current fpm image used by D-Laravel has also compiled opcache.so, and it can be used after adding it to php.ini.

If you want to use Xdebug and OPCache together, you must load Xdebug after OPCache.



For example: below.
extension=opcache.so
extension=xdebug.so



In addition, the latest php version 7.2.1 image does not support xdebug, so you cannot use the xdebug.so extension function in php version 7.2.1.




    
        livewire/content-tags
        
            
                
                    
                        
                            Tags:
                                                            laravel
                            
                        
                    
                    
                        	
                        	
                        	
                                                    	
                            
                    

                

                
                
                    
                        
                            
                                
                                    
                                
                                
                            
                        
                        
                            Devin Yang
                            Feel free to ask me, if you don't get it.:)
                        
                        
                            Follow
                        
                    
                
            
        
    
    
    

    livewire/comments

        
            
                
                                    No Comment
                                  
                                
            
            Post your comment
                        
              Login is required to leave comments

wordpress, d-laravel, docker, docker-compose

How to install Wordpress with D-Laravel

An 8-minute teaching video, introducing the installation of Wordpress on D-Laravel. D-Laravel is a docker-compose Laravel framework development environment, but it does not mean that it cannot be used to install other things. This video introduces the use of D-Laravel to install non-Laravel PHP projects, You can learn the usage of related instructions on D-Laravel: ./create --host usage, docker-compose up -d and ./console mysql usage, The database connection setting method after D-Laravel v1.0.0.

laravel

How can I force Laravel to use HTTPS urls

The problem I encountered is probably this. The container environment runs Laravel, and there is no HTTPS in the container, which causes Laravel to transmit the form without https. Add the following syntax to the boot of AppServiceProvider\URL::forceScheme('https');

laravel,dotenv,seo

How do I dynamically load different dotenv files in Laravel according to the subdomain name

Before we start, let me complain. Originally, my website could automatically display different languages according to the user's browser. That's okay, but Google's SEO doesn't seem to like it. He recommends using different URLs for each language and not using cookies or browser settings to adjust the content of the page. Well, I'll just be obedient. His suggested method, the first solution: distinguish by country, such as example.tw or example.de, how is this really impossible, or buy the registered domain name, or take all the domain names and no one will take it The strange domain name is more likely. The second solution: use sub-domain names to distinguish, this is what I am going to do, and so on to explain how to do it in Laravel. The third solution: example.com/tw/ and the like, Apple seems to do it this way. The fourth solution: site.com?loc=tw and the like are not recommended, indeed I think this is not a good idea.